[SPARK-54648][BUILD][4.0] Upgrade Jersey to 3.0.18 #53403
Conversation
LuciferYang
left a comment
LuciferYang
left a comment
There was a problem hiding this comment.
+1, LGTM (pending tests)
|
FYI, @pan3793 ,
To @LuciferYang and @peter-toth , I intentionally didn't backport this PR to the old branches initially because I'd like to hold this until we make Apache Spark 4.1.0 successfully. We can merge this after we finish to verify via Apache Spark 4.1.0 release. If you look at the branch-4.1, you will know that there exist several additional patches which I didn't backport in the same reasons. |
|
@dongjoon-hyun, this is actually a combination of SPARK-53223 and SPARK-51543 from the backport perspective, should I add both of their original descriptions? |
Hi, @pan3793 . Thank you for double-checking. However, we don't consider in that accumulated way. This is a simple and obvious backport of Jersey 3.0.18 dependency change (one-liner) with regenerated result of If there is any other code change, it might be consider as you mentioned. There is no other code contribution from SPARK-51543, isn't it? |
|
SPARK-51543: (master) upgrade Jersey from 3.0.16 => 3.0.17 then the current state is good enough, it's ready to go.
|
### What changes were proposed in this pull request? This PR aims to upgrade `jersey` to 3.0.18 . This is a backport of the following. - #51949 ### Why are the changes needed? To bring the latest bug fixes. - eclipse-ee4j/jersey@3.0.17...3.0.18 - eclipse-ee4j/jersey#5891 (Support Java 25) - eclipse-ee4j/jersey#5822 - https://projects.eclipse.org/projects/ee4j.jersey/releases/3.0.18 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #53403 from pan3793/SPARK-54648. Authored-by: Cheng Pan <chengpan@apache.org> Signed-off-by: yangjie01 <yangjie01@baidu.com>
|
Merged into branch-4.0. Thanks @pan3793 @dongjoon-hyun and @peter-toth |
4 participants
What changes were proposed in this pull request?
This PR aims to upgrade
jerseyto 3.0.18 .This is a backport of the following.
jerseyto 3.0.18 #51949Why are the changes needed?
To bring the latest bug fixes.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.